Skip to content

Add RPC API endpoint env#156

Merged
KaloyanTanev merged 3 commits into
mainfrom
diogo/add-eth1-flag
Aug 13, 2025
Merged

Add RPC API endpoint env#156
KaloyanTanev merged 3 commits into
mainfrom
diogo/add-eth1-flag

Conversation

@DiogoSantoss
Copy link
Copy Markdown

Add CHARON_EXECUTION_RPC_API_ENDPOINT env

@DiogoSantoss DiogoSantoss self-assigned this Aug 12, 2025
Copy link
Copy Markdown

@OisinKyne OisinKyne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also add it to the three .env..sample files like

# An Ethereum L1 RPC to validate operators using smart contract wallets
#CHARON_EXECUTION_CLIENT_RPC_ENDPOINT=

Comment thread docker-compose.yml Outdated
- CHARON_LOKI_ADDRESSES=${CHARON_LOKI_ADDRESSES:-http://loki:3100/loki/api/v1/push}
- CHARON_LOKI_SERVICE=charon
- CHARON_NICKNAME=${CHARON_NICKNAME:-}
- CHARON_EXECUTION_RPC_API_ENDPOINT=${CHARON_EXECUTION_RPC_API_ENDPOINT:-}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like we should default to the EL right here in the stack, currently that's `

Suggested change
- CHARON_EXECUTION_RPC_API_ENDPOINT=${CHARON_EXECUTION_RPC_API_ENDPOINT:-}
- CHARON_EXECUTION_RPC_API_ENDPOINT=${CHARON_EXECUTION_RPC_API_ENDPOINT:-"http://nethermind:8545}

also, the flag is execution-client-rpc-endpoint if the docs are right, so shouldn't it be CHARON_EXECUTION_CLIENT_RPC_ENDPOINT ?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, Kalo's #149 changes this to el-nethermind so we need to change this or kalo's pr should change it after this goes in

Copy link
Copy Markdown
Author

@DiogoSantoss DiogoSantoss Aug 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah right, I looked at the (eth1) PR description but it had the flag outdated

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to push it with nethermind and then after kalo's PR rebase we change it to el-nethermind

@KaloyanTanev KaloyanTanev merged commit b0f30fa into main Aug 13, 2025
3 checks passed
@OisinKyne OisinKyne deleted the diogo/add-eth1-flag branch February 27, 2026 11:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants